Add SOC2 critical vendor exit evidence gates#2273
Open
Errordog2 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Skill Improvement ($50-150 Bounty)
Skill Modified
Skill name:
soc2-gapSkill path:
skills/compliance/soc2-gap/What Was Wrong
The SOC 2 gap skill covered vendor inventories, risk assessments, SOC report collection, and DPAs/BAAs under CC9.2, but it did not require audit-ready evidence for critical vendor concentration risk or exit readiness.
That leaves a practical SOC 2 readiness gap: a company can collect annual SOC reports while still having a sole-source vendor dependency, no tested data export/restore path, no termination/deletion evidence, no subservice dependency monitoring, and no owner or risk acceptance for unresolved concentration risk.
Related review issue: #2239
What This PR Fixes
soc2-gapto1.0.1.CC9.2 Critical Vendor Concentration and Exit Evidence Gatewith an evidence matrix.Critical Vendor Exit Matrixdeliverable to the main output format.Evidence
Before: CC9.2 could be scored primarily from vendor policy, questionnaires, SOC report review, inventory, and contract terms.
After: Critical vendors now require explicit evidence for dependency concentration, fallback/exit owner, tested export or restore, subservice review, and formal risk acceptance for unresolved concentration risk before the control is treated as fully managed.
Test Cases Added/Updated
tests/vulnerable/)tests/benign/)This compliance skill does not currently have a fixture/test directory; the change keeps scope to the existing SOC 2 guidance files.
Validation
git diff --check.github/workflows/lint-skills.ymlindex.yamlfile-existence check matching.github/workflows/validate-index.ymlskills/androles/1.0.1,Critical Vendor Exit Matrix, concentration analysis, portability test, subservice dependency monitoring, risk acceptance, and CC9.2 critical vendor gate textBounty Tier
Bounty Info
Fixes #2239